home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
COMM
/
CBOX11.ARJ
/
CHATBOX.DOC
< prev
next >
Wrap
Text File
|
1991-08-10
|
45KB
|
1,037 lines
------------------------------------------------------------------
| |
| |
| |
| |
| |
| ChatBox Version 1.1 |
| |
| Split-Screen Sysop Chat - Caller Page Door |
| |
| |
| For |
| |
| PCBoard Versions 14.5 & 14.5a |
| |
| |
| Horizontal or Vertical Split-Screen Chat |
| |
| |
| Sysop Configurable Page Sounds (Beeping, Telephone Ringing) |
| |
| |
| Sysop may choose Flashing "Silent Page" Mode |
| |
| |
| Uses PCBTEXT - Completely Language Compatible |
| |
| |
| Seamless Appearance when used as a "Shelled-to" Door |
| |
| |
| All Options Are Sysop-Configurable |
| |
| |
| |
| ChatBox Version 1.1 |
| |
| (C) Copyright 1991 Yandell Computer Services |
| |
| 12121 Little Road - Bldg. 303 - Suite 212 |
| Hudson, FL 34667 |
| |
| DATA -- (813) 842-8099 (HST) |
| |
| |
| August 10, 1991 |
| |
| |
| |
------------------------------------------------------------------
--------------------------------------------------------------------
ChatBox
--------------------------------------------------------------------
TABLE OF CONTENTS Page
----------------- ----
INTRODUCTION
------------
1.0 What Is ChatBox 3
1.1 What Is New in Version 1.1 3
1.2 Multi-Nodes, Networks, Multi-taskers 3
INSTALLING ChatBox
------------------
2.0 Preliminaries 4
2.1 Configuring PCBoard Door Files 4
2.2 Setting Up Door Batch Files 5
2.3 Running CBSETUP and Creating CHATBOX.CNF 6-9
2.4 Setting Up for Sysop Initiated Chats 10
2.5 Setting Up for Multi-Language Use 11
2.6 Setting Up V.I.P. Callers (CHATBOX.VIP) 11
2.7 Setting Up PCBoard for an Alternate Chat Device. 11
RUN-TIME CONSIDERATIONS
-----------------------
3.0 Notes Regarding PCBTEXT Files 12
3.1 Notes Regarding the F4 Function Key 13
3.2 Notes Regarding SOUND.BAT 13
3.3 Notes Regarding Text File Displays 13
MISCELLANEOUS
-------------
4.0 Sysop Function Keys 14
4.1 Technical Notes 14
4.2 Caller Log Entries 14
4.3 Error Messages 15
4.4 Where to Receive Assistance 15
4.5 Disclaimer and Warranty 15
4.6 About the Author 15
4.7 Acknowledgments 16
4.8 Revision History 16
REGISTRATION
------------
5.0 Registering ChatBox 16
--------------------------------------------------------------------
Page 3 ChatBox Page 3
--------------------------------------------------------------------
1.0 What is ChatBox
--------------------
ChatBox is a Split-Screen chat utility designed for PCBoard. The
Sysop may select the Split-Screen format for chatting. In horizontal
mode, the screen is split into two halves (boxes), upper and lower.
In vertical mode, the screen is split into two halves (boxes), left
and right.
The Sysop may initiate the chat. ChatBox will bypass its paging
process and go directly into chat mode if initiated by the Sysop.
Split-Screen chatting allows simultaneous typing between the Sysop
and the caller.
ChatBox allows the Sysop to select the type of sound made when a
caller is paging. A different tone may be selected for the familiar
"beep-beep", or one of several different telephone ringing sounds
may be chosen. A special "silent mode" may be selected which flashes
a large white box on the screen. This mode is especially helpful for
hearing impaired Sysops. Sysops may choose to "shell" to their own
noise making or screen flashing program to alert them a caller is
requesting an on-line chat.
Three different paging time periods may be configured for each day
of the week.
Split-Screen chat colors may be configured by the Sysop (registered
copies of ChatBox only).
ChatBox uses PCBTEXT for multi-language compatibility and additional
flexibility.
ChatBox is completely DESQview aware.
ChatBox works with non-standard com ports automatically.
1.1 What is new in version 1.1
-------------------------------
Please refer to the enclosed file FEATURES.NEW for a list of new
features in ChatBox version 1.1.
1.2 Multi-nodes, networks, multi-taskers
-----------------------------------------
ChatBox has been developed in a networked environment. All multi-
node features are thoroughly tested on our own multi-node PCBoard
system. Two of ChatBox's primary beta test facilities are twenty
node systems.
ChatBox is DESQview aware. It is automatically detected, screen and
keyboard I/O are "well behaved", and time slices are given back to
other applications while ChatBox is idle.
--------------------------------------------------------------------
Page 4 ChatBox Page 4
--------------------------------------------------------------------
2.0 Preliminaries
------------------
Create a directory or subdirectory where you normally place doors.
Extract the entire contents of CBOX11.ZIP into this location.
2.1 Configuring PCBoard Door Files
-----------------------------------
Install a door called PAGE into your DOOR.LST file using PCBSETUP.
Answer the following questions as follows:
USER DOOR
Filename Password Sec Login SYS SYS Shell Path to DOOR Files
-------- -------- --- ----- --- --- ----- ------------------
#) PAGE 10 N Y N Y (if appropriate)
Note the use of PAGE as a door name, not CHATBOX, as you will most
likely want to place PAGE as a command on your main menu (BRDM).
A password would usually not be required for your PAGE door.
A low security level is required, as you may also be using this
same door when you wish to initiate a chat with the caller. ChatBox
follows the security level for the "O" command in PCBoard. Callers
who are below this level will not be able to use ChatBox to page
you.
A USERS.SYS file MUST be created. ChatBox will not run without it,
as ChatBox NEVER touches the USERS file.
A DOOR.SYS file is NOT needed.
If running PCBoard 14.5a, shelling is HIGHLY recommended because it
greatly increases the speed at which PCBoard returns when the caller
exits from ChatBox. ChatBox has been specifically designed as a
"Shell" door. Setting up ChatBox as a "swapped shell" door is not
recommended unless it is needed due to memory limitations. ChatBox
only requires about 69K of memory so "swapping" the "shell to" door
should not be required.
If you have different DOOR.LST files in your conferences, you will
need to configure the PAGE door in them also.
It is up to the individual Sysop as to whether or not to place the
PAGE command in the doors menu, or as a command on the main menu, or
both. The recommended usage is to place PAGE on the main menu and
not in the doors menu.
--------------------------------------------------------------------
Page 5 ChatBox Page 5
--------------------------------------------------------------------
2.2 Setting up door batch files
--------------------------------
The purpose of this section is to explain the command line calling
syntax for ChatBox. Please refer to the PCBoard manual for a more
complete discussion on door batch file installation. If you have
named the door PAGE (recommended) the following examples would be
the contents of your door file named PAGE.
*PREFERRED METHOD* (fast load!)
-------------------------------
@echo off
C:\CHATBOX\CHATBOX.EXE CHATBOX.CNF C:\PCB
---------------------- ----------- ------
| | |-> This node's home directory.
| |
| |
| ---------> The name of the configuration
| file. Enter a file NAME only.
| NEVER place a location here.
|
-------> The executable file name. Placing its location
in-line as shown results in MUCH faster response
time in executing the door.
The two lines above are all that is required to execute ChatBox when
running as a shelled-to door in PCBoard 14.5a. If you are not
running PCBoard 14.5a or you are not running ChatBox as a shelled-to
door, add the call to BOARD.BAT as the third command in the door
file Do NOT end your door file with BOARD.BAT if running ChatBox as
a shell-to door in PCBoard 14.5a.
*OLD FASHIONED METHOD* (tried and true, but slow load)
------------------------------------------------------
@echo off
d:
cd\chatbox
CHATBOX.EXE CHATBOX.CNF C:\PCB
c: ------
cd\pcb |-> This node's home directory.
The above method will work fine with ChatBox. The only drawback is
the slower loading time as a result of the changing of drives and
directories in DOS. As with the "preferred method", only add
BOARD.BAT to the end of the door file if you are NOT shelling to
ChatBox in PCBoard 14.5a, or if you are running PCBoard 14.5.
--------------------------------------------------------------------
Page 6 ChatBox Page 6
--------------------------------------------------------------------
2.3 Running CBSETUP and creating CHATBOX.CNF
---------------------------------------------
Enclosed with ChatBox 1.1 is a file called CBSETUP.EXE. This file
allows you to easily and quickly configure ChatBox configuration
files. Only one CHATBOX.CNF file is required for all nodes. Please
refer to section 2.5 page 11 for information on creating CHATBOX.CNF
files for multi-language use.
To start CBSETUP.EXE, enter CBSETUP CHATBOX.CNF at your DOS prompt
(CHATBOX.CNF would be the appropriate configuration file).
Each parameter in CBSETUP is described on the following pages.
* ChatBox registration number
---------------------------
This is the registration number received when ChatBox is registered.
Registration causes the ChatBox [ UNREGISTERED COPY ] message and
the brief delay at program termination to disappear. This message is
not replaced with your board name or anything else. The entire line
completely disappears for a true, seamless, "looks like PCBoard"
process if running as a shelled-to door in PCBoard 14.5a.
Registration also allows ChatBox to use the Sysop defined colors for
Split-Screen chat operations.
* Default chat screen type
--------------------------
You may select the initial type of Split-Screen chat mode to begin
the on-line chat session in. The valid selections are:
(1) Horizontal Split-Screen. The Sysop will be in the top half of
the screen, the caller will be in the bottom half.
(2) Vertical Split-Screen. The Sysop will be in the left hand side
of the screen, the caller will be in the right hand side.
(3) Regular non-split screen. Self explanatory.
(4) Vertical Split-Screen if caller is at 9600+ baud, Horizontal
Split-Screen if caller is less than 9600 baud.
ChatBox will begin the chat in the mode specified here unless the
caller is at or below the baud rate specified in the "Baud rate for
regular chat" parameter. If the caller is at or below this baud
rate, the chat will begin in the regular, non-split screen mode.
If it is determined that the caller's communications program is not
ANSI capable, ChatBox will start the chat in the regular, non-split
screen mode.
Section 2.3 continues on the next page
--------------------------------------------------------------------
Page 7 ChatBox Page 7
--------------------------------------------------------------------
2.3 Running CBSETUP and creating CHATBOX.CNF (continued)
---------------------------------------------------------
* Sound made when Sysop is paged
--------------------------------
You may select the type of sound ChatBox will make while paging.
(1) The familiar "beep beep".
(2) The familiar "beep beep, with a lower tone than #1.
(3) European telephone ring. Two short rings.
(4) Telephone ring. Low pitch.
(5) Telephone ring. Medium pitch.
(6) Telephone ring. High pitch.
(7) Silent - Flashing box on screen.
(8) Shell - Use another program or device for sounds or screens.
Press F2 at this parameter to listen to the sound you have selected.
If selecting #8 (shell) see page 13 section 3.2 for instructions on
creating SOUND.BAT.
* Baud rate for 'Regular' chat
------------------------------
If the caller is at this baud rate or less, ChatBox will begin in
the regular (non-split screen) chat mode. Scrolling separate parts
of the screen (required in Split-Screen chat) will usually yield
unfavorable results to callers connecting at 300 and 1200 baud.
Valid entries here are 300, 1200, 2400, and 9600. ChatBox will
always start in non-split screen mode if the caller is at 300 baud.
* Name to Display for Sysop
---------------------------
While in Split-Screen chat, this name is used to identify the Sysop
in the status line for the Sysop's half of the screen.
This name is used in the introductory "Hello, this is _____" text.
This is also used if the Sysop drops to DOS in ChatBox. It will be
displayed in front of appropriate "___ has exited to DOS" message.
* Color to use for Chat Text
----------------------------
Chat text (text the Sysop and caller type while chatting) colors may
be configured. This color is used when the caller is in color mode.
Pressing F2 at this parameter in CBSETUP will display a color chart
and sample Split-Screen chat display using the colors you've chosen.
Chat text colors are always high intensity (bright).
ChatBox must be registered for this toggle to be recognized. In an
unregistered copy, this will default to "2" when ChatBox is run.
Section 2.3 continues on the next page
--------------------------------------------------------------------
Page 8 ChatBox Page 8
--------------------------------------------------------------------
2.3 Running CBSETUP and creating CHATBOX.CNF (continued)
---------------------------------------------------------
* Color to use for Box Lines
----------------------------
Box line (lines creating the chat "box" while chatting) colors may
be configured. This color is used when the caller is in color mode.
Pressing F2 at this parameter in CBSETUP will display a color chart
and sample Split-Screen chat display using the colors you've chosen.
Chat text colors are always high intensity (bright).
ChatBox must be registered for this toggle to be recognized. In an
unregistered copy, this will default to "6" when ChatBox is run.
* Color for Sysop and Caller Name
---------------------------------
The Sysop and caller names are placed in the "box" lines separating
each "box". This color is used when the caller is in color mode.
Pressing F2 at this parameter in CBSETUP will display a color chart
and sample Split-Screen chat display using the colors you've chosen.
Name colors are always high intensity (bright).
ChatBox must be registered for this toggle to be recognized. In an
unregistered copy, this will default to "6" when ChatBox is run.
* Reason Prompt (or NONE)
--------------------------
If ChatBox is being used to page the Sysop, this optional parameter
may be used to ask the caller to briefly state the reason they are
paging the Sysop.
If this parameter is blank or NONE is entered, this question will be
disabled in ChatBox.
If the Sysop is initiating the chat, this parameter is ignored.
A file name may be specified in this parameter by starting the left
most position with a % followed by a file. If you specify a file, do
NOT specify a location. The file must reside with CHATBOX.EXE. For
example:
%WHY.TXT Briefly state the reason for this chat?
Section 2.3 continues on the next page
--------------------------------------------------------------------
Page 9 ChatBox Page 9
--------------------------------------------------------------------
2.3 Running CBSETUP and creating CHATBOX.CNF (continued)
---------------------------------------------------------
* Unavailable Text
------------------
This text is displayed when F4 is toggled off, when the caller does
not have a sufficient access level to request a chat, or when a page
attempt goes unanswered. For example:
The Sysop is not currently available for chat.
The above is displayed to the caller and written to the CALLER log.
A file name may be specified in this parameter by starting the left
most position with a % followed by a file. Do NOT specify a location
with the name. The file must reside with CHATBOX.EXE. For example:
%NO.TXT No one is available for a chat.
NO.TXT is displayed to the caller, the text is written to CALLER(x).
* Hours Text
------------
This text is displayed when a caller is requesting a chat outside of
the hours allowed for the particular day of the week. For example:
Paging is allowed hh:mm - hh:mm. Please leave a comment.
The above is displayed to the caller and written to the CALLER log.
A file name may be specified in this parameter by starting the left
most position with a % followed by a file. Do NOT specify a location
with the name. The file must reside with CHATBOX.EXE. For example:
%HOURS.TXT Page is not available at this hour.
HOURS.TXT is displayed to caller, the text is written to CALLER(x).
* Page Start and Stop Times
---------------------------
You may enter 3 page starting and stopping times for each day of the
week. Times must be entered in HH:MM format, where HH is a value of
0 through 23, and MM is a value of 0 through 59. CBSETUP performs
minimal testing of the hours input here. Care should be taken to
insure the times which are input are valid and in the HH:MM format.
To disable paging on a particular day, simply set the page times for
PERIOD 1 on that day a minute apart, such as 12:00 - 12:01, and set
the start and stop times for PERIOD 2 and 3 to the same time.
For 24 hour paging, set PERIOD 1 to the same start and stop times.
PERIOD 2 or 3 is ignored if the start and stop times are the same.
The TAB key rotates through different PERIODS in the same day.
--------------------------------------------------------------------
Page 10 ChatBox Page 10
--------------------------------------------------------------------
2.4 Setting up for Sysop initiated chats
-----------------------------------------
For the Sysop to initiate an on-line chat using ChatBox, all that
needs to be done is for the Sysop to type PAGE <enter> at the
PCBoard main prompt. While ChatBox is loading, you must quickly
press any key on the local keyboard. When ChatBox loads and sees the
keystroke waiting in the local system's keyboard buffer, it knows
the Sysop is initiating the chat and immediately starts in chat mode
instead of "paging" mode.
For this to function properly with all callers, you must install the
PAGE door in PCBoard so that all callers can access it with a low
security in DOOR.LST. ChatBox will follow the security level for
PCBoard's "O" command whenever a caller tries to page using ChatBox.
* Sysop Initiated Chat - AUTOMATED Method #1 :
Using PCBSETUP, you may define the ten SHIFT-FUNCTION keys (SHIFT-F1
through SHIFT-F10). This is an ideal and fast way for the Sysop to
bring up the PAGE command on the caller. Bring up PCBSETUP and
choose one of these keys, (SHIFT-F10 will probably be easiest to
remember - F10 for PCBoard chat, SHIFT-F10 for ChatBox). These are
located on the Options 2 page in PCBSETUP. To install the PAGE
command, simply enter the following:
F-Key #10 : PAGE ^M
The ^M must be entered exactly as shown.
Whenever you wish to chat with caller, press SHIFT-F10, then press
any key while ChatBox is loading to bypass the page mode and start
directly in chat mode (as described in the first paragraph above).
It is not possible for the caller to bring up ChatBox using this
method, as the caller is never capable of placing keystrokes in the
local (host) keyboard while ChatBox is loading.
* Sysop Initiated Chat - AUTOMATED Method #2 :
Enclosed with CBOX11.ZIP are files called SET_F10.EXE and
SET_F10.DOC. SET_F10 is a TSR designed to be installed in BOARD.BAT
before calling PCBoard. It detects Sysop F10 key presses and asks
if the Sysop wants to issue the PAGE command or use PCBoard's chat
facility. SET_F10 is a separate program that is released with the
ChatBox program. SET_F10.DOC contains all installation and operating
instructions. No part of this manual (CHATBOX.DOC) other than this
paragraph pertains to the SET_F10 program.
--------------------------------------------------------------------
Page 11 ChatBox Page 11
--------------------------------------------------------------------
2.5 Setting up for multi-language use
--------------------------------------
ChatBox uses text from PCBTEXT or appropriate language files with
the exception of the text that is used in CHATBOX.CNF. To make any
text in CHATBOX.CNF language compatible, simply create a duplicate
CHATBOX.CNF file except give it the appropriate EXTension. For
instance with French, use the appropriate French in CHATBOX.FRE and
ChatBox will automatically use CHATBOX.FRE instead of CHATBOX.CNF as
the configuration file. You do not need to worry about what ChatBox
is passed in the door file. If passed CHATBOX.CNF and the language
is .FRE, ChatBox will look for CHATBOX.FRE before using CHATBOX.CNF.
2.6 Setting up V.I.P. callers (CHATBOX.VIP)
--------------------------------------------
To create a VIP list of callers who may page at any time, create a
text file called CHATBOX.VIP. It must reside in the same location as
CHATBOX.EXE. To install special names into CHATBOX.VIP, simply enter
the names one at a time, with each name beginning on a new line.
Callers who appear in CHATBOX.VIP will be able to page the Sysop at
any time regardless of page time settings.
Callers who are listed in CHATBOX.VIP will NOT be able to PAGE the
Sysop if the F4 page bell toggle has been turned off in PCBoard. It
is assumed that if the Sysop has turned F4 off then he\she really
doesn't wish to disturbed.
2.7 Setting up PCBoard for an alternate chat device.
-----------------------------------------------------
It is not necessary to disable PCBoard's "O" command in order for
ChatBox to function. However, if you wish to use ChatBox exclusively
then follow these simple steps.
1) Set record #128 in all PCBTEXT files to:
"Please use the PAGE command for paging"
2) Use PCBSETUP to set the page times in PCBOARD.DAT to one minute
apart, for example 12:00 - 12:01.
When a caller presses "O" in PCBoard, they will receive the "Please
use the PAGE command" instruction contained in record #128 of the
appropriate PCBTEXT file.
--------------------------------------------------------------------
Page 12 ChatBox Page 12
--------------------------------------------------------------------
3.0 Notes regarding PCBTEXT files
----------------------------------
ChatBox detects the language being used and uses the following text
from the appropriate PCBTEXT (PCBTEXT.???) file.
Rec# Default text
97 Page ends in 30 seconds. (Ctrl-K) Aborts .
Notes: Self explanatory.
175 Sysop CHAT active at~
Notes: Written to caller log only. Time is added to end.
219 Sysop CHAT ended at~
Notes: Written to caller log and displayed after a chat. Time
is added to end of line.
327 I'm back! Thanks for waiting~
Notes: Displayed on return from Sysop F5. Caller's first name
is added to end of the line.
333 Hello, This is @OPTEXT@.~~
Notes: Displayed in Sysop's "box" when a chat begins. Chatbox
will replace @OPTEXT@ with Sysop's name in CBSETUP.
409 Operator paged at~
Notes: Written to caller log only. Time is added to the end
of the line, followed by the REASON the caller paged
(if used).
418 Press (Enter) to continue
Notes: Self explanatory.
436 ______ has exited to DOS. Please wait ...
Notes: Displayed when Sysop F5'd to DOS. Sysop's name in
CBSETUP is added to the beginning of the line.
ADDITIONAL NOTES:
-----------------
@FIRST@ (caller's first name) may be used in any line.
ChatBox replaces ~ characters with hard spaces in the same fashion
PCBoard does in PCBTEXT.
The text used from PCBTEXT files is simple informational text.
ChatBox does not support the use of %FILENAME conventions in any of
the above PCBTEXT parameters.
--------------------------------------------------------------------
Page 13 ChatBox Page 13
--------------------------------------------------------------------
3.1 Notes Regarding The F4 Function Key
----------------------------------------
ChatBox follows the F4 toggle from PCBoard. This allows the Sysop to
easily toggle paging on or off at any time.
The Sysop may also set the F4 toggle while in ChatBox.
To determine if you have F4 toggled ON in PCBoard, look at PCBoard's
call waiting screen. The very center information block will indicate
whether "Page Bell is Off" or "Page Bell is On". If you are in
PCBoard locally or a caller is on-line, you can determine if F4 is
toggled on by the (B) on the very bottom status line. There may be a
"P" or "A" in the parenthesis with the "B", (PAB), (AB), etc.
depending on how other toggles are set in PCBoard. If a "B" is
there, the page bell is toggled on.
3.2 Notes regarding SOUND.BAT
------------------------------
SOUND.BAT is called if #8 has been selected for the type of sound to
make when paging. ChatBox will shell out to SOUND.BAT every couple
of seconds instead of making a selected noise.
This allows the Sysop to make their own noise, screen displays, etc.
Note: We have received reports that sound cards have been
successfully used to create page sounds in SOUND.BAT. It should be
noted that this process could have difficulties. It would not be
surprising if the drivers which typically must be loaded for sound
cards to work created problems with communications programs. Test
carefully thoroughly if you plan on using a sound card to create
page sounds.
In all cases, keep whatever is placed in SOUND.BAT small and fast.
3.3 Notes regarding text file displays
---------------------------------------
ChatBox will display text files if indicated in certain text prompts
in CBSETUP. These text files support PCBoard color macros. Because
ChatBox has been designed to be as small as possible for "shell to"
door purposes, ANSI capabilities in these text files have been
intentionally omitted.
These text files also support the use of the @cls@ clear screen
macro, as well as the use of @first@ for the caller's first name.
Support for a mutlitude of @info@ macros has been intentionally
omitted to keep memory consumption as low as possible for use in
"shell to" door processes.
--------------------------------------------------------------------
Page 14 ChatBox Page 14
--------------------------------------------------------------------
4.0 Sysop function keys
------------------------
ChatBox follows F3 (printer on/off), F4 (page bell on/off) and F9
(display on/off) toggles from PCBoard. If F3 is on, ChatBox will
print any information sent to the caller log to the printer also. If
F9 is off, ChatBox will clear the screen after an unsuccessful page
attempt. The F4 key is explained in detail elsewhere in this manual.
Sysops may drop to DOS using the F5 key if F5 drop to DOS is enabled
in PCBSETUP for the node.
4.1 Technical notes
--------------------
ChatBox has been designed to run specifically with PCBoard versions
14.5 & 14.5a. ChatBox will not run with earlier versions of PCBoard
or with other brands of software.
Carrier is monitored by ChatBox. Should a caller drop carrier while
in ChatBox they will be returned to PCBoard, which will detect the
"no carrier" status and cycle appropriately.
ChatBox works with non-standard com ports ,addresses, and IRQs. COM1
is address 3F8/IRQ 4. COM2 is address 2F8/IRQ 3. If a COM port other
than 1 or 2 is used, ChatBox will use the address and IRQ
information as indicated in PCBOARD.DAT for the node.
ChatBox gives chat time credit while the Sysop is chatting with a
caller.
If it is detected that the caller's communications program is not
ANSI capable, ChatBox will start the chat in the regular, non-split
screen chat mode. A message will appear on the Sysop's screen if
this occurs.
4.2 Caller log entries
-----------------------
ChatBox makes pertinent entries into the caller log as follows:
If a REASON for paging is requested, the caller's answer is appended
to the "Operator Paged at" text and written to the CALLER files.
The "Hours available" text from CBSETUP is written to CALLER files
if a page is attempted outside of paging times.
The "Unavailable text" from CBSETUP is written to CALLER files if
the caller lacks security to page, if F4 page is OFF, or if the
Sysop does not answer a page attempt.
Also see section 3.0 page 12 for other text which is written to
CALLER files by ChatBox.
--------------------------------------------------------------------
Page 15 ChatBox Page 15
--------------------------------------------------------------------
4.3 Error messages
-------------------
ChatBox gives verbose installation error messages, such as invalid
paths. These messages appear and there is a short pause while they
are displayed.
4.4 Where to receive assistance
--------------------------------
There are two ways to receive assistance should it be needed.
YCS Support System - Home of ChatBox 813-842-8099 HST
Sound Advice Information Services 816-436-4516 HST
816-436-8029 Hayes
Sound Advice is available through PC Pursuit and StarLink networks.
Leave a message to Brent Yandell in the YANDELL conference,
currently conference #10 on Sound Advice. Please understand that
while we call Sound Advice regularly, we do not call there everyday.
If your need for assistance is urgent, please direct the matter to
the YCS Support System.
4.5 Disclaimer and warranty
----------------------------
ChatBox is a shareware product. ChatBox may be uploaded to BBS
systems as long as copyright notices are not removed and no changes
are made to the program. There are no warranties, expressed or
implied, for unregistered copies of ChatBox. Sysops who install
ChatBox on their systems assume any and all liabilities for anything
which may result as a consequence of running ChatBox. For registered
copies of ChatBox, Yandell Computer Services warrants that ChatBox
will perform as described in this documentation. In the event that
ChatBox does not perform as specified, Yandell Computer Services may
elect to fix ChatBox or refund the amount paid, if notified within
30 days of registration.
Under no circumstances shall Yandell Computer Services or the author
of ChatBox be liable for any loss of profit or any other damages,
including but not limited to special, incidental, consequential, or
other damages, arising out of the use or inability to use ChatBox.
PCBoard is a registered trademark of Clark Development Co. Inc.
DESQview is a registered trademark of Quarterdeck Office Systems.
4.6 About the author
---------------------
L. Brent Yandell has been involved in telecommunications for five
years, and has been writing, updating, and continuously supporting
BBS `doors' for four years. Many Sysops will be familiar with PCBFV,
the popular PCBoard File Viewer, and QReader, the `full screen' text
door for PCBoard.
--------------------------------------------------------------------
Page 16 ChatBox Page 16
--------------------------------------------------------------------
4.7 Acknowledgments
--------------------
Appreciation and many thanks are in order for the following people:
Roy Timberman of Sound Advice Information Systems for making his
twenty node system completely available for testing ChatBox, and for
providing a conference area for its support.
Jim Brewer for overall project review.
Tim Yandell for editing and proofing this documentation.
A special thanks to all ChatBox beta testers.
4.8 Revision history
---------------------
Date Version Details
-------- ------- -------
06-14-91 1.0 ChatBox initial release.
08-10-91 1.1 See the enclose FEATURES.NEW file.
5.0 Registering ChatBox
------------------------
ChatBox is not free software. ChatBox must be registered no later
than 30 days after installation.
Registration is $15.00 and may be paid by check, money order, Visa,
Mastercard, American Express, or Discover. If registering by credit
card on-line you will receive your registration number INSTANTLY!
Registration removes the [UNREGISTERED COPY] message at program
termination along with the corresponding brief delay. Registration
also enables the use of Sysop definable colors for Split-Screen chat
operations.
Refer to the enclosed file ORDER.FRM for complete registration
instructions.